Thanks for the bugfix.

I don't see this warning on my terminal, could you please post the following:

uname -a
Darwin Peters-MacBook-Pro-2.local 21.3.0 Darwin Kernel Version 21.3.0: Wed Jan  5 21:37:58 PST 2022; root:xnu-8019.80.24~20/RELEASE_X86_64 x86_64 i386 Darwin

grep --version
grep (BSD grep, GNU compatible) 2.6.0-FreeBSD

I wonder if we can use this pattern which seems much easier to read:

grep -Ev '^$|^#' .env

or maybe this to maintain backwards compatibility:

grep -v '^\s*[$#]' .env

Also wondering why the pipe still needs to be escaped \| 🤷

I don't have a link to the doc handy right now, but the | needs to be escaped in order to combine both patterns with a logical or. This can easily be tested with this, which should result in only one line bar and not in a blank one or in #:

echo '
#
bar' | grep -v '^$\|^\s*#'

The pattern grep -v '^\s*[$#]' .env does unfortunately not remove blank lines.

I'm using Arch Linux, the exact versions are:

$ uname -a
Linux yodaTux 6.2.1-arch1-1 #1 SMP PREEMPT_DYNAMIC Sun, 26 Feb 2023 03:39:23 +0000 x86_64 GNU/Linux

$ grep --version
grep (GNU grep) 3.8
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Mike Haertel and others; see
<https://git.sv.gnu.org/cgit/grep.git/tree/AUTHORS>.

As we have the comment note: strips comments and empty lines just before the pattern, I don't think that it's too problematic if the grep pattern is not super easy to read. So I would rather keep backward compatibility.

Apart from that, grep -Ev '^$|^#' .env seems to work 👍

One last thing: We are currently removing blank lines as well as lines having # as first non-whitespace character. This leaves lines starting with whitespace characters not directly followed by # untouched. Some examples are:

• a=b
• ab

Inside env_load_stream() we then split the lines by the first occurrance of =. So and ab result in errors there. But a=b would result in export " a=b". This causes export to fail with export: a=b': not a valid identifier`.

So, all cases are covered. But I think it would be good to document this a bit better.